<p>This rule raises an issue when Angular input properties are given different names (aliases) than their actual property names.</p>
<h2>Why is this an issue?</h2>
<p>Aliasing input bindings creates confusion between the template usage and the component implementation. When an input property has a different name
in templates than in the component class, it becomes harder for developers to understand the relationship between the two.</p>
<p>This inconsistency makes code maintenance more difficult, especially when multiple developers work on the same codebase. It also breaks the
principle of least surprise, where developers expect the template binding name to match the property name.</p>
<p>The practice can lead to debugging difficulties when developers search for property usage but cannot find template references due to the name
mismatch.</p>
<h3>What is the potential impact?</h3>
<p>Code becomes harder to understand and maintain. Developers may struggle to trace the connection between template bindings and component properties,
leading to increased development time and potential bugs during refactoring.</p>
<h3>How to fix in Angular?</h3>
<p>Remove the alias and use the property name directly in both the component and template. This creates a clear, consistent naming convention.</p>
<h4>Non-compliant code example</h4>
<pre data-diff-id="1" data-diff-type="noncompliant">
@Component({})
class MyComponent {
  @Input('userName') name: string; // Noncompliant
}
</pre>
<h4>Compliant code example</h4>
<pre data-diff-id="1" data-diff-type="compliant">
@Component({})
class MyComponent {
  @Input() userName: string;
}
</pre>
<p>For the new input() function, remove the alias option and use the property name directly.</p>
<h4>Non-compliant code example</h4>
<pre data-diff-id="2" data-diff-type="noncompliant">
@Component({})
class MyComponent {
  name = input('', { alias: 'userName' }); // Noncompliant
}
</pre>
<h4>Compliant code example</h4>
<pre data-diff-id="2" data-diff-type="compliant">
@Component({})
class MyComponent {
  userName = input('');
}
</pre>
<p>In the inputs array, use the property name without aliasing syntax.</p>
<h4>Non-compliant code example</h4>
<pre data-diff-id="3" data-diff-type="noncompliant">
@Component({
  inputs: ['name: userName'] // Noncompliant
})
class MyComponent {}
</pre>
<h4>Compliant code example</h4>
<pre data-diff-id="3" data-diff-type="compliant">
@Component({
  inputs: ['userName']
})
class MyComponent {}
</pre>
<h3>Documentation</h3>
<ul>
  <li> <a href="https://github.com/angular-eslint/angular-eslint">Angular ESLint</a> - Rule <a
  href="https://github.com/angular-eslint/angular-eslint/blob/main/packages/eslint-plugin/docs/rules/no-input-rename.md">no-input-rename</a> </li>
  <li> Angular Input Decorator - <a href="https://angular.dev/api/core/Input">Official documentation for the @Input decorator</a> </li>
  <li> Angular Component Inputs - <a href="https://angular.dev/guide/components/inputs">Guide on using inputs in Angular components</a> </li>
</ul>
